Monster Media 1994 #2

home *** CD-ROM | disk | FTP | other *** search

/ Monster Media 1994 #2 / Monster Media No. 2 (Monster Media)(1994).ISO / renegade / rgep261.zip / RGEP.EXE / RGE.DOC < prev next >

Wrap

Text File | 1994-06-12 | 22KB | 469 lines

Renegade Editor is Copyright 1994 by Patrick Spence All Rights Reserved Renegade is copyright 1994 by Cott Lang. This set of programs, and all of its accompanying files excluding FileIN and FileINs associate files are Copyright 1994 by Patrick Spence, all rights are reserved. FileIN is copyright 1994 by Chris Roberts, all rights reserved. You are granted the limited license to evaluate this program on ONE computer for a period of 21 days. IF by the end of the 21 day evaluation period you decide that it is not worth registering, then you must cease using the program, and remove all unarchived copies of it from your system. You may still distribute the distribution archive. Under no condition are you allowed to edit, modify, reverse engineer, or otherwise change the files in the distribution archive (excepting archival purposes). Such actions constitute a license violation, and your license to use RGE is immediately revoked. You do not need to use an executable file compressor such as LZExe, PKLite or ExePack, since the program has been compressed and protected, and -ANY FURTHER MODIFICATIONS WILL CAUSE THE PROGRAM TO CEASE FUNCTIONING-. You may freely distribute the distribution archive as LONG AS you do NOT add any files (especially BBS advertisements) to the archive, or modify any of the files in the archive. Plus, if you find an archive that has an advertisement added to it, send it to me, and if I can validate that an advertisement or other file was added without permission, (and assuming no one has reported that particular one before you), you may receive a discount on registering Renegade Editor, or credit towards registering OTHER KludgeWare! files. Registration gives you the limited license to run one copy of this program at a time, on ONE machine at a time. Ergo, no more than one copy may be in use at a given time. The registration key remains the property of Patrick Spence, and you may not transfer it, give it away, nor distribute it without explicit permission from Patrick Spence. If you wish to purchase a site license, or other type of usage agreement that is different than stated here, send me a letter detailing what you want, and I will give you the terms for the agreement. ┌───────────────────────────────────────────────────────────────────┐ │ WARRANTY/GUARANTEE │ └───────────────────────────────────────────────────────────────────┘ None. I have made every effort to make this program as safe as possible, but there will always be that one situation that I cannot test on my machine, or on the machines of my beta testers. So, this program is only guaranteed to take up space on your drive. ! WARNING ! ! WARNING ! ! WARNING ! ! WARNING ! ! WARNING ! ! WARNING ! This program is intended for Renegade sysops who have a modicum of experience with Renegade, and WHO MAKE BACKUPS ON A REGULAR BASIS! RGE -Will- be a dangerous program if you don't know what you are doing, as it will let you do things and save changes without intervention because it assumes that you know what you are doing. If you in any way fell uncomfortable with this program, and the potential hazards, OR, if you do not make regular backups of your data files, then DO NOT RUN THIS PROGRAM because I will NOT be responsible for any damages that are done to your BBS as a result. YOU HAVE BEEN WARNED! ! WARNING ! ! WARNING ! ! WARNING ! ! WARNING ! ! WARNING ! ! WARNING ! ┌───────────────────────────────────────────────────────────────────┐ │ DISTRIBUTION │ └───────────────────────────────────────────────────────────────────┘ This program may be freely distributed as LONG AS you do NOT add more files to, or take files away from, or change any of the files in the distribution archive. ADVERTISEMENT FILES ARE EXPRESSLY FORBIDDEN FROM BEING ADDED. Registered owners may NOT distribute their registration keys to anyone without writen permission from Patrick Spence. Registered owners may SELL their keys, but MUST notify Patrick Spence in writing that they are transferring their key, as well as send a copy of the registration form filled out with the information from the person that they are selling it to (so that a new key can be generated) ┌───────────────────────────────────────────────────────────────────┐ │ REGISTRATION │ └───────────────────────────────────────────────────────────────────┘ Registration of the RGE package is simple, fill out the accompanying REGISTER.FRM and send it to me with $25.00 american at: Patrick Spence P.O. Box 637 Apache Junction, AZ 85217-0637 You will receive back a receipt with your registration key, and the name used to generate it. Type this name EXACTLY as it appears on the form, or your registration key will not work. See the REGISTER.FRM file to see if any 'Early Bird' Specials are in effect that will give you a reduction of costs. Registration entitles you to no cost upgrades to any future versions. This means that in most cases, the registration will be valid across versions, but in some cases, you will need to send me a small fee to receive your upgrade. This is entirely dependant on how much changes across versions. No guarantees are made that there will be future releases, but I do not see any immediate ceasation of production on at least SOME piece of software. I am working on more utilities to include, as well as more features of the renegade editor. No matter what, I will continue to support the RGE package with assistance in using it, and possible bug fixes as long as my computer operates. Registered users WILL get more support and assistance than those who do not register. ┌───────────────────────────────────────────────────────────────────┐ │ INSTALLATION │ └───────────────────────────────────────────────────────────────────┘ It is advised that you dedicate a directory for RGE, but it is not required. You do not need to place it in the path, and you do not need to place it in your Renegade directory. Run the RGECFG program that is provided in this package. This program will let you enter your path to your Renegade BBS, as well as customize how the RGE looks (including 43/50 line mode on ega/vga machines). If you have registered the RGE package, this is also how you enter your user name and registration key. When entering your user name and registration key, type them EXACTLY as they appear on the registration certificate, case -IS- significant. To select an item to change, just scroll up and down and hit <Enter> on the selection that you wish to change. An editing field will pop up in the lower window to allow you to change the item. While scrolling up and down, the right end of the Highlight bar will have one of three arrows () to tell you if there is more options above and below the current line. This will also be how the scroll bar works in the RGE program itself. This version of RGE does -NOT- have any crippled features, and for the term of your trial testing period, it doesn't have any nag screens. Some time after your trial registration, RGE will cease to operate, requiring a registration. Future releases will have restricted features that you will not be able to access without registering the RGE package. To run RGE, merely type in its name at the command line, or you could install it to be called by one of your GLOBATx.BAT files, so you can call it from inside Renegade with a function key. WARNING, Renegade does not currently reread the Renegade.dat upon return from a shell, and as such, the changes you have made will not necessarily be used until you open Renegades internal system configuration option and exit it. RGE does no comm port communication, so you can only run it locally. ┌───────────────────────────────────────────────────────────────────┐ │ RUNNING RGE │ └───────────────────────────────────────────────────────────────────┘ ┌──────────────────────────┐ │ CONVENTIONS USED / NOTES │ └──────────────────────────┘ - Saving your changes: When you edit an area, such as the strings, or the system configuration, and you want the changes that you have made saved, you MUST save them prior to returning to the main menu. If you don't you will lose all of the changes that you have made. RGE will prompt you upon exit of each main section if you want to save the changes or not. If you select N it will abort the exit, and will NOT save any changes. If you select Y it will save changes and then exit, and if you select A it will Abort any changes you have made, and exit the section. - String Editing: Strings are interactively edited, and you can use the following command keys while doing so: Key Result ───────────────────────────────────────────────────────── Ins Toggles Insert/Overstrike mode RGE defaults to Insert mode Home Sends the cursor to the beginning of the field Left Arrow Moves the cursor one space left Right Arrow Moves the cursor one space right Control-Backspace Deletes entire field End Sends cursor to the end of the field Esc Returns string to previous value. It will remain editing the field, so you can easily return to the values you had before you started changing the string. - Moving among screens: When moving among screens when editing multi screen data, such as the archive configuration, the strings, and the protocols, you can use the following keys: End Go to last active screen Home Go to the first active screen Left Arrow Moves one screen left Right Arrow Moves one screen right - Color Translations: RGE does NOT actively translate Renegade color codes, and this is a FEATURE, not a bug. The original impetus for writing this program was to be able to interactively edit various strings in Renegade interactively, and be able to change individual characters without having to retype the whole string. If you want to see what a color translated version of any of the strings will be, then simply hit <F10> while you are editing any of the fields. This will pop up a color translation screen that will have the string displayed, as well as a listing of all the Pipe codes, and the default ^x codes in the Renegade configuration. - Renegade and RGE: Currently, -Renegade- does NOT re-read the Renegade.dat file upon return from a shell such as a Globatx.bat or a Door drop file, so if you use one of these to shell out to run RGE, your changes will not be evident until you either exit Renegade or load up the system config and exit it...if you do the latter, do not change anything in the system config. This is a hassle, but hopefully Cott will reconfigure Renegade to re-read the Renegade.dat file upon return from the shell. Until then, use some common sense, and keep track of what you are doing. - MULTI TASKING WARNING!: RGE support supports basic file sharing, but intellegence and care must STILL be taken, since it goes beyond the range of ordinary utilities, and as such, you can lose configured data if you are not careful. - MESSAGE BASE AND FILE BASE EDITING: RGE can now edit message and file bases. The method used for this uses a lot of RAM to work with, so some of you might not be able to use this option. You will need about 450k of conventional ram to use this option. You can also only edit -1024- bases, the maximum number of bases RG will support if you have base number compression on. If enough of you actually have/use more than 1024 message or file bases, let me know and I will work up a different method. - OVERLAYS RGE uses overlays, this is so more people can use the message and file base editing routines. RGE will swap its overlays to EMS is there is enough available, otherwise it will use conventional ram for its overlays. - LOG FILE RGE makes a text format log file giving the general activities that were done in each RGE session. The log file can be turned off in the RGECFG program. The log is formatted like this: ---------- Thu, Apr 14, 1994 RGE > 01:10:50 The Renegade Editor is Copyright 1994 by Patrick Spence > 01:10:50 All Rights Reserved > 01:10:50 Please read the documentation for full license agreement ---------- Sun, Apr 24, 1994 RGE ? 20:41:00 Using EMS for faster overlay swapping. | 20:41:00 Error number loading SCHEME.DAT is: 0 > 20:41:13 Entering Protocol edit < 20:41:16 Exiting Protocol edit > 20:41:17 Entering Messagebase configuration. < 20:41:23 Exiting Messagebase configuration. 20:41:24 Normal Termination The various character codes at the start of most lines are as follows: ? Warning of some sort ! Fatal error # RGE had a question - Start of session + Creation of something - Destruction of something @ Change of something > Entry to a section < Exit of a section $ WHAT? you haven't Registered? | Debug statement (normally not in production code) ┌───────────────────────────────────────────────────────────────────┐ │ MESSAGE BASE TEMPLATE │ └───────────────────────────────────────────────────────────────────┘ There is now a message base template function, so that you may create a template to use when inserting new message bases. Using this you can make it easier to add in a large number of similar bases (such as echomail bases) to your configuration. This function is activated by the letter T from the main message base editing screen. Included in this archive is a sample template, to use it just place it in the same directory that you run RGE from, and when you enter the message base area, it will prompt you for use of it. ┌───────────────────────────────────────────────────────────────────┐ │ POST IT NOW AUTOMATIC POSTER │ └───────────────────────────────────────────────────────────────────┘ Another portion of the RGE package is an automatic message posting program named PIN (or Post It Now). PIN used to be distributed separately, but is now part of the overall package. Previous PIN configuration files (PIN.CFG) will -not- work with this version. The maximum file size that you can post is approximately 64k in size. This is due mainly to the limit of message size in Renegade. Pin currently truncates the text file information at its size limit, though future versions may just continue with another message. Remember though, that even though PIN will post a 60k text file into a message, many mail processors (such as squish) have a lower limit on the size of a message. ┌───────────────────────────────────────────────────────────────────┐ │ PIN AND FILEIN! │ └───────────────────────────────────────────────────────────────────┘ Due to a cooperative effort, and a modular approach to programming, FileIN by Chris Roberts now supports posting a message announcing files to a renegade message base. This posting is done via a shelled call to PIN, so in order to take advantage of this feature of FileIN! you will need to have Pin installed. ┌───────────────────────────────────────────────────────────────────┐ │ RUNNING PIN │ └───────────────────────────────────────────────────────────────────┘ Before PIN can be used, you must have an RGE.CFG file in the directory that you run it from. That way PIN can find the Renegade directory. Refer to previous sections of this documentation for more information on creating a RGE.CFG file. PIN is operated quite easily, you create a text file that contains the name of the file you want posted, the base name (as defined in renegade), the subject of the message, who it is from and who it's to. The format of the configuration file is as follows: Line 1: <Who the message is from> Line 2: <Who the message is to> Line 3: <Subject of the message> Line 4: <Base name> Line 5: <file name/path to post> like this: Your Sysop All Message Traffic announce tossrept.txt This can be repeated as many times in one file as you desire for multiple posts in one run. It is -VERY IMPORTANT- that you do not have any empty lines, even at the end of the file, as it will cause an error. Any valid definitions before a bad line (such as a blank line, or a forgotten line) will still be posted though. After creating this configuration file, you can then run PIN one of two ways: PIN <Configuration file> PIN The first option runs PIN, if there isn't a configuration file, it will create one. <Configuration file> is the text file of posting info. The Second option will display a short help screen. This method of specifying the configuration text file on the commandline will allow you to have different messages posted at different times (like weekly and monthly reports). ┌───────────────────────────────────────────────────────────────────┐ │ FILEIN - FILES.BBS IMPORTER BY CHRIS ROBERTS │ └───────────────────────────────────────────────────────────────────┘ The FileIN Files.bbs importer written by Chris Roberts is now being distributed inside the RGE package (As well as separately). This is being done in this manner, because we want to be able to bring you a full complement of Renegade Utilities all in one package. ┌───────────────────────────────────────────────────────────────────┐ │ SUPPORT │ └───────────────────────────────────────────────────────────────────┘ The RGE package is only supported directly by me in the ITC Renegade base, Locally on my BBS, in netmail, or in snail mail to the same address that you send registrations to. Hawks Aerie BBS : (602) 873-2755 14.4 - MNP 1..5 - V.32b - V.42b ITC Net Address : 85:20/0 Fido Net Address : 1:114/252 Strange Net Address : 84:84/1 Liberty Net Address : 76:48/42 ┌───────────────────────────────────────────────────────────────────┐ │ KUDOS │ └───────────────────────────────────────────────────────────────────┘ Many thanks to my beta team, as well as those who have assisted in one form or another to get this program released. KludgeWare! Beta Team: (Partial List) Bob Shields - 85:823/200 @ ITC Net Jerry Bursztyn - 84:62/200 @ Strange Net(tm) Chris Roberts Assistance by: (Partial List) Cott Lang (Thanks Cott!) Richard Rector Frank Ward Eric Kimmet Jack Reece ┌───────────────────────────────────────────────────────────────────┐ │ ANTICIPATED FEATURES: │ └───────────────────────────────────────────────────────────────────┘ I am constantly working on more features for the RGE package, and intend to ultimately include editing of ALL of the data files in Renegade. Next on the listing is file ENTRY editing. I hope to have a 1-900 system set up to make it easier to register the software that I write. This will allow me to place an online registration door up on my BBS to instantly give you a registration Key.